﻿@{
    ViewBag.Title = "Nservice Bus - Publisher and Subscriber";
    Layout = "~/Views/Shared/_Layout.cshtml";
}
        <ol class="breadcrumb" style="margin-top: 10px;">
    <li><a href="/Home/Jome">Home</a></li>
    <li><a href="/NServiceBus/Introduction/">Nservice Bus</a></li>
    <li class="active">Publisher/Subsriber</li>
</ol>
            <div id="Pub/Sub">
                <h3><strong>Publisher and Subscriber In NServiceBus</strong></h3>
                <ul>
                    <li>One of the common assumptions about pub/sub messaging is that it involves physical one-to-many communication.�The only thing is, that at the physical level pub/sub isn't that interesting.NServiceBus Provide logical level pub/sub.</li>
                    <li><br /><img src="~/Images/NServiceBus/pubsub.png" class="img-thumbnail" height=100% width=100% /><br></li>
                    <li><br />In Above Diagram Publisher Khow They are Interested and � the publisher stores their addresses so that�it knows where to send which message.</li>
                    <li><br />When requested by applicative logic to publish a message, the NServiceBus infrastructure contacts its configured subscriptions�database, finds all the subscriber endpoints registered for the given message type, and dispatches a physical message to each one.</li>
                    <li><br />Since one-way messaging is used to dispatch physical messages, even if one of the subscriber endpoints is offline or otherwise unavailable, this does not cause the publishing thread to block. The message is stored in the sending machine's outgoing queue (for a configurable period of time), while the messaging infrastructure attempts to deliver the message to its destination.</li>
                    <li><br />each subscriber gets its own distributor and each of them decides independently to which machine it passes its messages.</li>
                </ul>
            </div>
            <div id="FullDuplex">
                <h3><strong>FullDuplex In NServiceBus</strong></h3>
                <ul>
                    <li>Full Duplex  In NServiceBus is Request-Response Communication.</li>
                    <li>In FullDuplex  The Client is going to Send the Message to the Server and the Server will Process Message and return it back to the Client.</li>
                    <li><br /><img src="~/Images/NServiceBus/FullDuplex.png" class="img-thumbnail" height=100% width=100% /><br></li>
                </ul>
            </div>
       
       
    